Bump operator deployment memory request/limit defaults#1561
Conversation
During start of the operators it is seen in some environments that the current defaults get reached during start/initialization. Checking the usage, most of them peaks at the startup, using between 350-380 MiB, other around 300MiB, for a short time and then it get stabilized at 200-210 MiB. Jira: OSPRH-17785 Signed-off-by: Martin Schuppert <mschuppert@redhat.com>
stuggi
requested review from
dprince
and removed request for
slagle and
viroel
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dprince, stuggi The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/cherry-pick 18.0-fr3 |
|
@stuggi: once the present PR merges, I will cherry-pick it on top of DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
openshift-merge-bot
Bot
merged commit fc9c4c2
into
openstack-k8s-operators:main
|
@stuggi: new pull request created: #1562 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
3 participants
During start of the operators it is seen in some environments that the current defaults get reached during start/initialization. Checking the usage, most of them peaks at the startup, using between 350-380 MiB, other around 300MiB, for a short time and then it get stabilized at 200-210 MiB.
Jira: OSPRH-17785